Morrison, R. et al

Eddy covariance measurements of carbon dioxide, energy and water fluxes at a commercial Miscanthus x. giganteus plantation, Lincolnshire, UK, 2008 to 2013

https://doi.org/10.5285/00487c70-b74e-4c91-ab0c-31735c2e3b13 Cite this dataset

This dataset contains time series observations of surface-atmosphere exchanges of net ecosystem carbon dioxide exchange (NEE), sensible heat (H) and latent heat (LE), and momentum (τ) measured at a at a Miscanthus x. giganteus Greef et Deu plantation in Lincolnshire, UK.

Turbulent flux densities were monitored using the micrometeorological eddy covariance (EC) technique between 30th April 2008 and 18th February 2013. The dataset includes ancillary weather and soil physics observations, as well as variables describing atmospheric turbulence and the quality of the turbulent flux observations.

This work was supported by the Natural Environment Research Council award number NE/R016429/1 as part of the UK-SCAPE programme delivering National Capability.

Publication date: 2019-09-12

Format

Comma-separated values (CSV)

Spatial information

Study area
Spatial representation type: Raster
Spatial reference system: WGS 84

Temporal information

Temporal extent: 2008-05-01 to 2013-02-18

Provenance & quality

Eddy covariance (EC) and micrometeorological observations were made above the Miscanthus canopy using an open-path eddy covariance system. Ancillary meteorological and soil physics observations were made from a scaffold tower at the northern end of the plantation.

Turbulent flux densities were calculated from the raw EC data using the EddyPRO® Flux Calculation Software Version 6.1.

Quality Control of EC data involved removal of statistical outliers and tests that theoretical requirements for the successful application of the EC technique were not violated significantly. Data gaps in EC data (NEE, LE, H) and the partitioning of NEE into gross ecosystem production and total ecosystem production were performed using the REddyProc Package for R (Reichstein et al., 2019).

Further details are available in the supporting documentation.